ARROW-9266: [Python][Packaging] Enable S3 support in macOS wheels#8315
ARROW-9266: [Python][Packaging] Enable S3 support in macOS wheels#8315kszucs wants to merge 4 commits into
Conversation
|
@github-actions crossbow submit wheel-osx-mavericks-cp36m wheel-osx-high-sierra-cp36m |
|
Revision: 430ffdf472b9420cdbb5784946e2ba0edaf2f5c8 Submitted crossbow builds: ursa-labs/crossbow @ actions-571
|
|
@github-actions crossbow submit wheel-osx-* |
|
Revision: 430ffdf472b9420cdbb5784946e2ba0edaf2f5c8 Submitted crossbow builds: ursa-labs/crossbow @ actions-572
|
|
@github-actions crossbow submit wheel-osx-* |
|
Revision: 50aaa55f306fd492cb743f011c9968860dbab2d8 Submitted crossbow builds: ursa-labs/crossbow @ actions-598
|
|
@kszucs please rebase |
|
@github-actions crossbow submit wheel-osx-* |
|
Revision: 16a9f0916e8a9c5e10e0f66a086ad54c84676d34 Submitted crossbow builds: ursa-labs/crossbow @ actions-604
|
|
@github-actions crossbow submit wheel-osx-* |
|
Revision: 97b5b32 Submitted crossbow builds: ursa-labs/crossbow @ actions-605
|
|
@github-actions crossbow submit wheel-osx-* |
|
The successful builds take between ~42-45 minutes but occasionally it exceeds the 50m build time limit. Sadly we can't utilize travis' build cache since crossbow always creates new branches and the fallback default branch won't have any cache entries. |
|
Revision: c40e6e4 Submitted crossbow builds: ursa-labs/crossbow @ actions-611
|
|
@github-actions crossbow submit wheel-osx-mavericks-cp38 |
|
Revision: 7bcd83e Submitted crossbow builds: ursa-labs/crossbow @ actions-613
|
Does this explain why some of the nightly builds seem to be intermittently missing certain macOS wheels? E.g., sometimes for example there's no cp38 wheel, only for that wheel to come back with the next nightly publish. |
We could run something on |
|
I think @nealrichardson is right: my understanding is that travis caching will try to pull from default branch if no cache is available for current branch, so the warming strategy could work. |
We would need to merge the latests tasks (multiple .travis.yml files into a single one) generated by crossbow to master automatically which would be rather complicated. Crossbow also creates diverged branches from master at the moment. We can make a jira about supporting CI caches in crossbow though I can't see a generic solution at the moment. |
Could you send me build links? I don't entirely see your question. |
4 participants
Depends on #8304